When you create certain objects by using the Schedule Manager's Deploy SAS DATA Step Program or the New Flow... option from the Actions menu, and you target a custom repository folder, the objects are not written to that repository. The objects are always written to the Foundation repository, even if you have specified a different value for the Location: field in the dialog box.

As a result, cross-repository associations are created between the object and the folder, because the object is in the Foundation repository whereas the folder it is linked with is in the location that you specified.

This issue occurs with these three object types: Job, Deployed Job, or Deployed Flow

Note: Changing the Repository: selector on the Plug-ins tab in SAS^® Management Console does not alter this behavior.

The cross-repository associations are a problem when you run certain batch tools to process any of the three object types or run the Validate SAS Folders tool within the Metadata Analyze and Repair utility.

Failures Occur with Batch Tools

Failures occur due to the cross-repository associations when you use certain batch tools, including any of the following:

• CopyObjects
• ExportPackage
• ImportPackage
• DeleteObjects
• MakeFolder

The exact error differs, depending on the tool used. The problem is most likely to be seen with the batch export tool. When you attempt to export an object that has cross-repository associations, a warning appears in the log. Here are the object-specific warnings:

WARN  The object "/Custom/TestJob(Job)" could not be found on the server.  
      It will not be exported.
WARN  The object "/Custom/TestJob(DeployedJob)" could not be found on the server.  
      It will not be exported.
WARN  The object "/Custom/TestFlow(DeployedFlow)" could not be found on the server.  
      It will not be exported.

Failures Occur with the Metadata Analyze and Repair Utility

When you run the Validate SAS Folders tool through the Metadata Analyze and Repair utility, the cross-repository associations result in warnings. Here are the object-specific warnings:

WARN The job "/Custom/TestJob" is contained within a different repository than its parent folder.
WARN The Deployed job "/Custom/TestJob" is contained within a different repository than its parent folder.
WARN The Deployed flow "/Custom/TestFlow" is contained within a different repository than its parent folder.

Hot Fix

Click the Hot Fix tab in this note to access the hot fix for this issue. However, this fix is not intended to repair the problem once it has occurred. The fix prevents the problem from occurring again.

Workaround

If you have already experienced this issue, contact SAS Technical Support for a workaround.

Operating System and Release Information

A fix for this issue for SAS Middle Tier 9.4_M2 is available at:

A fix for this issue for SAS Management Console 9.4_M2 is available at: